Documentation fixes after the removal of the legacy C API #1439
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Madhunika-atmakuri
approved these changes
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
@swift-nav/algint-team
sbp_register_callback()andsbp_register_frame_callback()no longer exist. They have been replaced withsbp_callback_register().sbp_msg_callback_thas changed tosbp_callback_tand it has a different function prototypesbp_frame_callback_thas been removedAPI compatibility
Does this change introduce a API compatibility risk?
No - it only changes documentation.
API compatibility plan
N/A
JIRA Reference
The removal of the legacy API is tracked in https://swift-nav.atlassian.net/browse/AP-1684